Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing vulnerabilities for source-salesforce - Premium support #27899

Closed
wants to merge 11 commits into from

Conversation

mauricioalarcon
Copy link
Contributor

CVE-2022-40897
https://security-tracker.debian.org/tracker/CVE-2023-29383
https://security-tracker.debian.org/tracker/CVE-2023-31484
https://security-tracker.debian.org/tracker/CVE-2016-2781

What

Changed source base image to use python:3.9-alpine3.18 instead of slim - Adjusted to update OS packages

How

Switched to use alpine based image

Recommended reading order

N/A

🚨 User Impact 🚨

Are there any breaking changes? What is the end result perceived by the user?
None expected, just more security

So far nothing breaks and all the test are passing on our side, I've bumped the minor version accordingly

If there are breaking changes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.

Pre-merge Actions

Expand the relevant checklist and delete the others.

New Connector

Community member or Airbyter

  • Community member? Grant edit access to maintainers (instructions)
  • Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors:<name>:integrationTest.
  • Connector version is set to 0.0.1
    • Dockerfile has version 0.0.1
  • Documentation updated
    • Connector's README.md
    • Connector's bootstrap.md. See description and examples
    • docs/integrations/<source or destination>/<name>.md including changelog with an entry for the initial version. See changelog example
    • docs/integrations/README.md

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

  • Create a non-forked branch based on this PR and test the below items on it
  • Build is successful
  • If new credentials are required for use in CI, add them to GSM. Instructions.
Updating a connector

Community member or Airbyter

  • Grant edit access to maintainers (instructions)
  • Unit & integration tests added

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

  • Create a non-forked branch based on this PR and test the below items on it
  • Build is successful
  • If new credentials are required for use in CI, add them to GSM. Instructions.
Connector Generator
  • Issue acceptance criteria met
  • PR name follows PR naming conventions
  • If adding a new generator, add it to the list of scaffold modules being tested
  • The generator test modules (all connectors with -scaffold in their name) have been updated with the latest scaffold by running ./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates then checking in your changes
  • Documentation which references the generator is updated as needed

roman-yermilov-gl and others added 10 commits June 30, 2023 21:18
* Source Zendesk Support: fix missing headers
…ehq#27883)

* improve words and add doc to sidebar

* update words in collecting metrics docs'
* changes

* update how to pr and readme

* update contributeing guides

* update code of conduct text

* update submit new connector

* submit new connector doc

* make one line for submit new conn find request

* improve words
…eries (airbytehq#27687)

* initial ctid for testing

* initial ctid for testing

* initial ctid for testing

* Automated Commit - Format and Process Resources Changes

* add version and state type to xmin status

* add logic to swtich between xmin and ctid sync

* npe fixes

* use enum

* refactor

* add relation node logic + validation for vacuuming + more refactor

* refine test + make PR ready for review

* remove un-wanted changes

* missed this one

* remove irrelevant comments

* add more assertions

* remove jdbc log

* address review comments

* 🤖 Auto format source-postgres code [skip ci]

* skip streams under vacuum

* 🤖 Auto format source-postgres code [skip ci]

* update log message

* 🤖 Auto format source-postgres code [skip ci]

* comment

* latest round of review comments

* missed this file

* 🤖 Auto format source-postgres code [skip ci]

* initial drop for testing

* test

* refactor query plan

* Add testing for query plan

* sanity

* sanity

* sanity

* remove change in spec json

* sanity

* test

* comment

* remove hardcoded testing value

* add test case

* revert json spec

* small imrovements

* typo

* fix test

* bump docker image version

* revert bump docker image version

---------

Co-authored-by: rodireich <rodireich@users.noreply.github.com>
Co-authored-by: subodh <subodh1810@gmail.com>
Co-authored-by: octavia-squidington-iii <octavia-squidington-iii@users.noreply.github.com>
Co-authored-by: Augustin <augustin@airbyte.io>
@CLAassistant
Copy link

CLAassistant commented Jun 30, 2023

CLA assistant check
All committers have signed the CLA.

@octavia-squidington-iii octavia-squidington-iii added the area/connectors Connector related issues label Jun 30, 2023
@github-actions
Copy link
Contributor

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

  • PR name follows PR naming conventions
  • Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan and you've followed all steps in the Breaking Changes Checklist
  • Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
  • Secrets in the connector's spec are annotated with airbyte_secret
  • All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
  • Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
  • The connector tests are passing in CI
  • You've updated the connector's metadata.yaml file (new!)
  • If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

  1. Check for hidden checklists in your PR description

  2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

@mauricioalarcon mauricioalarcon marked this pull request as ready for review June 30, 2023 23:45
@mauricioalarcon mauricioalarcon changed the title Fixing vulnerabilities for source-salesforce Fixing vulnerabilities for source-salesforce - Premium support Jun 30, 2023
@sajarin
Copy link
Contributor

sajarin commented Jul 3, 2023

@mauricioalarcon can you sign the cla, add an entry to the salesforce.md docs and bump the version in the metadata.yaml file?


ENTRYPOINT ["python", "/airbyte/integration_code/main.py"]

LABEL io.airbyte.version=2.1.0
LABEL io.airbyte.version=2.1.1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you bump the metadata and documentation changelog? I'll trigger the tests to validate the change.

@marcosmarxm marcosmarxm added the team/tse Technical Support Engineers label Jul 4, 2023
@marcosmarxm
Copy link
Member

Running tests in #27954

@mauricioalarcon
Copy link
Contributor Author

Sorry guys @marcosmarxm , @sajarin - while trying to add my email to have the CLA signed ended bringing some other changes - I'm closing this one in favor of #28021 with the same change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

10 participants